1z0-067: Upgrade Oracle9i/10g/11g OCA OR OCP to Oracle Database 12c OCP

You want to export the pluggable database (PDB) hr pdb1 from the multitenant container database (CDB)CDB1 and import it into the cdb2 CDB as the emp_pdb1 PDB.

Examine the list of possible steps required to perform the task:

Create a PDB named emp_pdb1.
Export the hr_pdb1 PDB by using the full clause.
Open the emp_pdb1 PDB.
Mount the emp_pdb1 PDB.
Synchronize the emp_pdb1 PDB in restricted mode.
Copy the dump file to the Data Pump directory.
Create a Data Pump directory in the emp_pdb1 PDB.
Import data into emp_pdb1 with the full and remap clauses.
Create the same tablespaces in emp_pdb1 as in hr_pdb1 for new local user objects.

Identify the required steps in the correct order.

2, 1, 3, 7, 6, and 8
2, 1, 4, 5, 3, 7, 6, 9, and 8
2, 1, 3, 7, 6, 9, and 8
2, 1, 3, 5, 7, 6, and 8

Correct answer: C

Explanation:

Because the step 2 says that you perfom an expdp with the full clause and you don’t need to create the tablespaces when you perform the impdp. FULL=yes will export tablespace definitions. So no need step 9. https://docs.oracle.com/cd/B10501_01/server.920/a96652/ch01.htm

You wish to create jobs to satisfy these requirements:

Automatically bulk load data from a flat file.
Rebuild indexes on the SALES table after completion of the bulk load.

How would you create these jobs?

Create both jobs by using Scheduler raised events.
Create both jobs using application raised events.
Create one job to rebuild indexes using application raised events and another job to perform bulk load using Scheduler raised events.
Create one job to rebuild indexes using Scheduler raised events and another job to perform bulk load by using events raised by the application.

Correct answer: C

Explanation:

The bulk loader would be started in response to a file watcher scheduler event and the indexes would be rebuilt in response to an application event raised by the bulk loader. https://docs.oracle.com/cd/E18283_01/server.112/e17120/scheduse005.htm#CIABIEJA Your application can raise an event to notify the Scheduler to start a job. A job started in this way is referred to as an event-based job. The job can optionally retrieve the message content of the event. https://docs.oracle.com/cd/B28359_01/server.111/b28310/scheduse008.htm#CHDIAJEB

Your Oracle 12c multitenant container database (CDB) contains multiple pluggable databases (PDBs). In the PDB hr_pdb, the common user c##admin and the local user b_admin have only the connect privilege.

You create a common role c##role1 with the create table and select any table privileges.

You then execute the commands:

SQL> GRANTc##role1 TOcMadmin CONTAINER=ALL;

SQL>CONNsys/oracle@HR_PDB assysdba

SQL> GRANTc##role1TO b_admin CONTAINER=CURRENT;

Which two statements are true?

C##admin can create and select any table, and grant the c##role1 role to users only in the root container.
B_admin can create and select any table in both the root container and kr_pdb.
c##admin can create and select any table in the root container and all the PDBs.
B_admin can create and select any table only in hr_pdb.
The grant c=»role1 to b_admin command returns an error because container should be set to ALL.

Correct answer: CD

Examine the commands executed in the root container of your multitenant container database (CDB) that has multiple pluggable databases (PDBs):

SQL> CREATE USER c##a_admin IDENTIFIED BY orcl123;

SQL> CREATE ROLE c##role1 CONTAINER=ALL;

SQL> GRANT CREATE VIEW TO C##roleI CONTAINER=ALL;

SQL> GRANT c##role1 TO c##a_admin CONTAINER=ALL;

SQL> REVOKE c##role1 FROM c##a_admin;

What is the result of the revoke command?

It executes successfully and the c##role1 role is revoked from the c##a_admin user only in the root container.
It fails and reports an error because the container=all clause is not used.
It executes successfully and the c##rocl1 role is revoked from the c##a_admin user in the root database and all the PDBs.
It fails and reports an error because the comtainer=current clause is not used.

Correct answer: B

Explanation:

SQL> REVOKE c##role1 FROM c##a_admin; REVOKE c##role1 FROM c##a_admin * ERROR at line 1: ORA - 01951: ROLE ‘C##ROLE1’ not granted to ‘C##A_ADMIN’ SQL> REVOKE c##role1 FROM c##a_admin CONTAINER=ALL; Revoke succeeded. SQL> This CREATE USER c##a_admin IDENTIFIED BY orcl123; will create common user event container is not specified.

Examine the RMAN command:

RMAN> CONFIGURE ENCRYPTION FOR DATABASE ON;

RMAN> BACKUP DATABASE PLUS ARCHIVELOG;

Which prerequisite must be met before accomplishing the backup?

The password for the encryption must be set up.
Oracle wallet for the encryption must be set up.
All the tablespaces in the database must be encrypted.
Oracle Database Vault must be enabled.

Correct answer: B

Explanation:

Configuration encryption will used by Transparent encryption. For transparent encryption, you will need to create a wallet, and it must be open. Transparent encryption will then occur automatically after you have issued the CONFIGURE ENCRYPTION FOR DATABASE ON or CONFIGURE ENCRYPTION FOR TABLESPACE ON command. http://docs.oracle.com/cd/E25054_01/backup.1111/e10642/rcmbckad.htm#CEGEJABHCONFIGURE ENCRYPTION : You can use this command to persistently configure transparent encryption. You cannot persistently configure dual mode or password mode encryption. SET ENCRYPTION : You can use this command to configure dual mode or password mode encryption at the RMAN session level.

Configuration encryption will used by Transparent encryption. For transparent encryption, you will need to create a wallet, and it must be open. Transparent encryption will then occur automatically after you have issued the CONFIGURE ENCRYPTION FOR DATABASE ON or CONFIGURE ENCRYPTION FOR TABLESPACE ON command.

http://docs.oracle.com/cd/E25054_01/backup.1111/e10642/rcmbckad.htm#CEGEJABH

CONFIGURE ENCRYPTION : You can use this command to persistently configure transparent encryption. You cannot persistently configure dual mode or password mode encryption. SET ENCRYPTION : You can use this command to configure dual mode or password mode encryption at the RMAN session level.

A database is running in archive log mode. The database contains locally managed tablespaces. Examine the RMAN command:

RMAN> BACKUP

AS COMPRESSED BACKUPSET

SECTION SIZE 1024M

DATABASE;

Which statement is true about the execution of the command?

The backup succeeds only if all the tablespaces are locally managed.
The backup succeeds only if the RMAN default device for backup is set to disk.
The backup fails because you cannot specify section size for a compressed backup.
The backup succeeds and only the used blocks are backed up with a maximum backup piece size of 1024 MB.

Correct answer: D

Explanation:

COMPRESSED enables binary compression. RMAN compresses the data written into the backup set to reduce the overall size of the backup set. All backups that create backup sets can create compressed backup sets. Restoring compressed backup sets is no different from restoring uncompressed backup sets. RMAN applies a binary compression algorithm as it writes data to backup sets. This compression is similar to the compression provided by many media manager vendors. When backing up to a locally attached tape device, compression provided by the media management vendor is usually preferable to the binary compression provided by BACKUP AS COMPRESSED BACKUPSET. Therefore, use uncompressed backup sets and turn on the compression provided by the media management vendor when backing up to locally attached tape devices. You should not use RMAN binary compression andmedia manager compression together. Some CPU overhead is associated with compressing backup sets. If the target database is running at or near its maximum load, then you may find the overhead unacceptable. In most other circumstances, compressing backup sets saves enough disk space to be worth the CPU overhead. SECTION SIZE sizeSpec Specifies the size of each backup section produced during a data file backup. By setting this parameter, RMAN can create a multisection backup. In a multisection backup, RMAN creates a backup piece that contains one file section, which is a contiguous range of blocks in a file. All sections of a multisection backup are the same size. You can create a multisection backup for a data file, but not a data file copy. File sections enable RMAN to create multiple steps for the backup of a single large data file. RMAN channels can process each step independently and in parallel, with each channel producing one section of a multisection backup set. If you specify a section size that is larger than the size of the file, then RMAN does not use multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections. Depending on where you specify this parameter in the RMAN syntax, you can specify different section sizes for different files in the same backup job. Note: You cannot use SECTION SIZE with MAXPIECESIZE or with INCREMENTAL LEVEL 1.

COMPRESSED enables binary compression.

RMAN compresses the data written into the backup set to reduce the overall size of the backup set. All backups that create backup sets can create compressed backup sets. Restoring compressed backup sets is no different from restoring uncompressed backup sets.

RMAN applies a binary compression algorithm as it writes data to backup sets. This compression is similar to the compression provided by many media manager vendors. When backing up to a locally attached tape device, compression provided by the media management vendor is usually preferable to the binary compression provided by BACKUP AS COMPRESSED BACKUPSET.

Therefore, use uncompressed backup sets and turn on the compression provided by the media management vendor when backing up to locally attached tape devices. You should not use RMAN binary compression andmedia manager compression together.

Some CPU overhead is associated with compressing backup sets. If the target database is running at or near its maximum load, then you may find the overhead unacceptable. In most other circumstances, compressing backup sets saves enough disk space to be worth the CPU overhead.

SECTION SIZE sizeSpec Specifies the size of each backup section produced during a data file backup.

By setting this parameter, RMAN can create a multisection backup. In a multisection backup, RMAN creates a backup piece that contains one file section, which is a contiguous range of blocks in a file. All sections of a multisection backup are the same size. You can create a multisection backup for a data file, but not a data file copy.

File sections enable RMAN to create multiple steps for the backup of a single large data file.

RMAN channels can process each step independently and in parallel, with each channel producing one section of a multisection backup set.

If you specify a section size that is larger than the size of the file, then RMAN does not use multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections.

Depending on where you specify this parameter in the RMAN syntax, you can specify different section sizes for different files in the same backup job.

Note: You cannot use SECTION SIZE with MAXPIECESIZE or with INCREMENTAL LEVEL 1.

In your database, the tbs percent used parameter is set to 60 and the tbs percent free parameter is set to 20.

Which two storage-tiering actions might be automated when using Information Lifecycle Management (ILM) to automate data movement?

The movement of all segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds tbs percent used
Setting the target tablespace to read-only after the segments are moved
The movement of some segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds TBS percent used
Taking the target tablespace offline after the segments are moved
The movement of some blocks to a target tablespace with a lower degree of compression, on a different storage tier, when the source tablespace exceeds tbs percent used

Correct answer: BC

Explanation:

The threshold for activating tiering policies is based on two parameters:TBS PERCENT USED TBS PERCENT FREE Both values can be controlled by the DBMS_ILM_ADMIN package. TBS PERCENT USED and TBS PERCENT FREE default to 85 and 25, respectively. Hence, whenever the source tablespace’s usage percentage goes beyond 85 percent, any tiering policy specified on its objects will be executed and objects will be moved to the target tablespace until the source tablespace becomes at least 25 percent free. Note that it is possible to add a custom condition to tiering policies to enable movement of data based on conditions other than how full the tablespace is. In addition, the READ ONLY option must be explicitly specified for the target tablespace.

The threshold for activating tiering policies is based on two parameters:

TBS PERCENT USED

TBS PERCENT FREE

Both values can be controlled by the DBMS_ILM_ADMIN package.

TBS PERCENT USED and TBS PERCENT FREE default to 85 and 25, respectively. Hence, whenever the source tablespace’s usage percentage goes beyond 85 percent, any tiering policy specified on its objects will be executed and objects will be moved to the target tablespace until the source tablespace becomes at least 25 percent free. Note that it is possible to add a custom condition to tiering policies to enable movement of data based on conditions other than how full the tablespace is.

In addition, the READ ONLY option must be explicitly specified for the target tablespace.

You want to consolidate backup information and centrally manage backup and recovery scripts for multiple databases running in your organization.

Which two backup solutions can be used?

RMAN recovery catalog
RMAN Media Management Library
Enterprise Manager Cloud Control
Enterprise Manager Database Express
Oracle Secure Backup

Correct answer: AC

Explanation:

Enterprise Manager allows a centralized control of database backups. It is possible to set up and schedule RMAN backups for all the databases in a large company, use a consistent backup strategy, and refer to all past RMAN output logs at any time, since they are stored in the Enterprise Manager Cloud Control repository. There is no need to use a central RMAN catalog, because information about the backups is centrally available from Enterprise Manager. And with the group backup feature new to Enterprise Manager Cloud Control 12c, it can be even faster to set up RMAN backups for all the databases-even if there are thousands-that are part of an Enterprise Manager group. http://www.oracle.com/technetwork/articles/oem/havewala-rman-em12c-2104270.html

Enterprise Manager allows a centralized control of database backups. It is possible to set up and schedule RMAN backups for all the databases in a large company, use a consistent backup strategy, and refer to all past RMAN output logs at any time, since they are stored in the Enterprise Manager Cloud Control repository. There is no need to use a central RMAN catalog, because information about the backups is centrally available from Enterprise Manager. And with the group backup feature new to Enterprise Manager Cloud Control 12c, it can be even faster to set up RMAN backups for all the databases-even if there are thousands-that are part of an Enterprise Manager group.

http://www.oracle.com/technetwork/articles/oem/havewala-rman-em12c-2104270.html

You want RMAN to make duplicate copies of data files when using the backup command.

What must you set using the RMAN configure command to achieve this?

MAXSETSIZE TO 2;
DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CHANNEL DEVICE TYPE DISK FORMAT '/disk1/%U' , '/disk2/%U';
DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;

Correct answer: D

Explanation:

Configuring Backup Duplexing You can use the CONFIGURE ... BACKUP COPIES command to specify how many copies of each backup piece should be created on the specified device type for the specified type of file. This type of backup is known as a duplexed backup set. The CONFIGURE settings for duplexing only affect backups of datafiles, control files, and archived logs into backup sets, and do not affect image copies. NOT A The CONFIGURE MAXSETSIZE command limits the size of backup sets created on a channel. This CONFIGURE setting applies to any channel, whether manually allocated or configured, when the BACKUP command is used to create backup sets. The default value is given in bytes and is rounded down to the lowest kilobyte value. Reference: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfa.htm#BRADV137

You create a table with the period for clause to enable the use of the Temporal Validity feature of Oracle Database 12c.

Examine the table definition:

create table employees

(empno number, salary number,

deptid number, name varchar2(100),

period for employee_time);

Which three statements are true concerning the use of the Valid Time Temporal feature for the EMPLOYEES table?

The valid time columns employee_time_start and employee_time_end are automatically created.
The same statement may filter on both transaction time and valid temporal time by using the AS OF TIMESTAMP and PERIOD FOR clauses.
The valid time columns are not populated by the Oracle Server automatically.
The valid time columns are visible by default when the table is described.
Setting the session valid time using DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIME sets the visibility for data manipulation language (DML), data definition language (DDL), and queries performed by the session.

Correct answer: ABC

Explanation:

Reference: https://docs.oracle.com/database/121/ARPLS/d_flashb_archive.htm#ARPLS74552

Vendor:	Oracle
Exam Code:	1z0-067
Exam Name:	Upgrade Oracle9i/10g/11g OCA OR OCP to Oracle Database 12c OCP
Date:	Jul 04, 2018
File Size:	499 KB

Download Upgrade Oracle9i-10g-11g OCA OR OCP to Oracle Database 12c OCP.1z0-067.PracticeDumps.2018-07-04.117q.vcex

How to open VCEX files?

Demo Questions

Question 1

Question 2

Question 3

Question 4

Question 5

Question 6

Question 7

Question 8

Question 9

Question 10

ProfExam at a 20% markdown